Waku 2024 H2 Roadmap update #117
Conversation
| section Nim.darshankabariya | ||
| %% TODO: review estimate | ||
| Nwaku on Windows: nwaku-windows-n, 2024-08-15, 6w | ||
| section Js.weboko |
There was a problem hiding this comment.
Are rln v2 and API stabilization efforts for later?
There was a problem hiding this comment.
Good catch! Fixed. Can you please help provide estimate for all js-waku items.
There was a problem hiding this comment.
Thanks for adding!
Won't we have API stabilization as a separate work stream? Though we discussed it - it is vaguely defined as we don't have any backlog for it. We can add it at the end of H2 as well so not to overcommit.
For estimates for dogfooding app I think 8w is good as it is aligned with beginning of Devcon.
For reliability all good as per waku-org/pm#186 (comment)
For rln v2 - I think 8w is good estimate but I am not sure as for the scope (in my mind it seems quite straightforward to do) so if possible I'd add 2w on top, if no we can go with current and extend if it is needed.
There was a problem hiding this comment.
Let's continue the planning discussion in discord
| Public dogfooding web app: milestone, after pub-dogfood-web-app-1 pub-dogfood-web-app-2, 0 | ||
| section Scale up number of Communities | ||
| Usage of rendezvous: milestone, after rendezvous-r, 0 | ||
| section Demonstrate product market-fit |
There was a problem hiding this comment.
One more thing that may belong here is finishing the Waku Whitepaper. This would roughly take the entire Q4 (12w) to finish, but be something that all Research engineers will work on in parallel to their other deliverables (a few hours each week).
There was a problem hiding this comment.
added to roadmap: https://docs.google.com/document/d/1L8HvXtAYk-JqQL6w3RgCskXwegcTa0J5nyH9YL4LrQE/edit#heading=h.hejfvov7j7ux but as you say here, not much value to have it in Gantt chart.
content/waku/2024-gantt.md
Outdated
| (simulation) Functionality and stress test store v3: sim-storev3, 2024-08-01, 8w | ||
| (simulation) relay reliability performance impact: sim-relay-rel, after sim-store-cmp sim-req-res, 4w | ||
| (simulation) req-res reliability performance impact: sim-reqres-rel, after sim-relay-rel, 6w |
There was a problem hiding this comment.
This still seems mostly accurate except that we'll need a (significant) separate item for Store Sync. Reliability performance testing could also probably be more general.
I'd change it to:
(simulation) Functionality and stress test store v3: sim-storev3, 2024-07-08, 8w
(simulation) Functionality and stress test store v3: sim-storesync, 2024-09-01, 10w
(simulation) Reliability performance impact: sim-rel, after sim-storesync, 10w
| %% Team legend: | ||
| %% task name: team (accountable person) | ||
| %% - r-*: research (jm-clius) | ||
| %% - t-*: telemetry (fryorcraken) | ||
| %% - n-*: nwaku (ivansete) | ||
| %% - j-*: js-waku (weboko) | ||
| %% - c-*: chat (plopezlpz) | ||
| %% - g-*: go-waku (fryorcraken) | ||
| %% - bd-*: BD (pedro) | ||
| %% - se-*: Solution Engineer (vpavlin) |
There was a problem hiding this comment.
For the next iteration I want the team leads to handle the Gantt Chart so set some names.
Which means everyone mentioned in this legend can check:
(1) In the Milestones overview with deliverables section, that every deliverable needed work from their team has a Gantt task with the right prefix after the keyword after. For example:
E2e reliability protocol Status integration: milestone, crit, after r-e2e-rel-status c-e2e-rel-status, 0
has work scheduled for research and chat team, but no work for js-waku and nwaku teams
(2) Then, ensure that the assignment of tasks to team members is roughly correct until 31 Dec 2024. What matters is the completion dates, as it is what is then committed to in roadmap.
No description provided.